home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000156_news@newsmaster….columbia.edu _Tue Oct 21 10:05:15 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA23004
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 21 Oct 1997 10:05:15 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA16025
for kermit.misc@watsun; Tue, 21 Oct 1997 10:05:15 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: login script beeps unexpectedly
Date: 21 Oct 1997 14:05:11 GMT
Organization: Columbia University
Lines: 82
Message-ID: <62icqn$582$1@apakabar.cc.columbia.edu>
References: <62ejvl$fpk$1@eskinews.eskimo.com> <62ft4g$j94$1@apakabar.cc.columbia.edu> <62h9lb$pbm$1@eskinews.eskimo.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:7934
In article <62h9lb$pbm$1@eskinews.eskimo.com>,
Jim Osborn <jimo@eskimo.com> wrote:
: In article <62ft4g$j94$1@apakabar.cc.columbia.edu>,
: Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
: >In article <62ejvl$fpk$1@eskinews.eskimo.com>,
: >Jim Osborn <jimo@eskimo.com> wrote:
: >: I use the following macro to connect with my ISP...
: >:
: >And which Kermit program are you using?
:
: Oops, sorry - C-Kermit 6.0...
:
: >It's not obvious from your script, but if INPUT ECHO is ON, and if the
: >service sends a beep character, then Kermit will echo it.
:
: I guessed that, so I double checked, and the ISP sends no beeps.
: I watched a cycle of at least five toxic modem offers, and got a beep
: on each cycle, so I'm pretty confident it's not a simple buffering
: issue, per your comments below. That is, it's not flushing a beep
: from a prior login attempt. When I say "beep" I'm really referring
: to the "echo \007" command, of course.
:
: >It just rings the bell or beeps, whatever your console is set up to
: >do normally when it gets an ASCII BEL character.
: >
: >: and the
: >: good old "echo \007" command? The effects are very different.
: >:
: >So you must be using Kermit 95. In this case, the BEEP command can produce
: >different sounds...
:
: Nope, Unix.
:
Well, then any difference between "beep" and "echo \007" is puzzling indeed.
In UNIX, "beep" translates, ultimately, to "putchar(\07);" and "echo \007"
becomes 'printf("%s", "\07");'. Both putchar and printf used buffered i/o,
and they are both printing the same thing.
OK, let's look at your script more closely:
: >: define eskimo {
: >: while not defined \%1 {
: >: askq \%1 {Eskimo Password: }
: >: }
: >: :retry
: >: dial 258-0759
You need an IF FAIL statement here. You don't want the script to keep
executing if your DIAL command fails.
: >: in 30 {Your Selection ==>} #Initial selector, choose service
Ditto.
: >: output 1\13 #Select Eskimo
: >: in 60 login: #Start login process
Ditto.
: >: out jimo\13 #Look for: Hello ,CLI,,27,xxx@seattle2
: >: clear input
: >: in 30 {Welcome to eskimo.com} #Read Annex ID string
Ditto. In fact, if this one fails, you can fall through the next test
and then (since the subsequent INPUTs are also untested), out comes the beep.
: >: xif \find({CLI,,27},\v(input)) { #Start over if toxic modem
: >: xif \find({@seattle2},\v(input)) {
: >: echo {Aborting 27,,2}
: >: goto retry
: >: }
: >: }
: >: in 30 Password:
: >: out \%1\13
: >: in 60 {Main Command?}
: >: out {!} #Start shell
: >: # beep #doesn't beep until escape back to kermit
: >: echo \007 #^G
: >: connect /quietly
: >: }
- Frank